Dynamic network  slice-switching and handover system and method

ABSTRACT

Aspects of the subject disclosure may include, for example, receiving a request to allow a wireless device accessing a network service by a first portion of a network to access the service via a second portion of the network operating within a different spectral region, wherein control operations are separate from data forwarding operations and configured to facilitate a forwarding of user data via the data forwarding operations. The first and second wireless spectral regions are different ones of managed and unmanaged spectral regions. The request is evaluated and a redirection of the forwarding of the user data facilitated via the data forwarding operations to the second portion of the network, responsive to the request, the request being initiated via the control operations, without interrupting the forwarding of the user data via the data forwarding operations. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/287,678, filed Feb. 27, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/590,656 filed on May 9, 2017, now U.S. Pat. No.10,257,668. The contents of the foregoing are hereby incorporated byreference into this application as if set forth herein in full.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a dynamic network slice-switching andhandover system and method.

BACKGROUND

Network providers typically offer platforms for third parties to deliverservices and applications to network subscribers. Communication networksenabled by technologies such as Network Function Virtualization (NFV)and Software Defined Networking (SDN), may be flexibly organized so asto serve various customer demands. In building advanced networks, suchas those to support future developments in wireless networks (includingnext generation, or so-called Fifth Generation (5G) wireless networks),network slicing provides the ability to create different virtualnetworks over which different traffic flows can travel isolated fromeach other. For example, a network slice can include a collection oflogical network functions that support a communication servicerequirement of a particular network service. Accordingly, differentvirtual networks, or slices, can support different services, differentusers and/or different types of user equipment (UE).

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of an example communicationnetwork for providing services to communication devices;

FIG. 2 depicts an illustrative embodiment of another examplecommunication network for providing services to communication devices;

FIGS. 3A-3B depicts illustrative embodiments of processes for managingnetwork resources used in portions of the system described in FIGS. 1and 2;

FIGS. 4-5 depict illustrative embodiments of communication systems thatprovide media services that can be used by the communication networks ofFIGS. 1-2;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1-2, and 4-5;

FIG. 7 depicts an illustrative embodiment of a communication device; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for using a control plane of a mobility network using aseparate control plane and user plane for each mobile service and/ormobile application to set up sessions and/or logical network slices foruser plane forwarding of user data during a dynamic slice switch andhandover between 3GPP and non-3GPP wireless networks. Other embodimentsare described in the subject disclosure.

One or more aspects of the subject disclosure include a mobile deviceincludes a processing system having a processor and a memory that storesexecutable instructions. The instructions, when executed by theprocessing system, facilitate performance of operations, that includeaccessing a mobile service by a first wireless access point operatingwithin a first radio frequency spectrum. The mobile service includescontrol plane operations and data plane operations of the first wirelessaccess point, wherein the control plane operations are separate from thedata plane operations and configured to facilitate a forwarding of userdata via the data plane operations. A second wireless access point isidentified operating within a second radio frequency spectrum, whereinthe first radio frequency spectrum includes one of a managed frequencyspectrum and an un-managed frequency spectrum, and wherein the secondradio frequency spectrum comprises a different one of the managedfrequency spectrum and the un-managed frequency spectrum. The accessingof the mobile service be transferred to the second wireless access pointis requested via the control plane operations and without interruptingthe forwarding of the user data via the data plane operations of thefirst wireless access point. A response to the request is received viathe control plane operations without interrupting the forwarding of theuser data via the data plane operations of the first wireless accesspoint. Responsive to the response indicating that second wireless accesspoint has been configured to accommodate a redirection of the forwardingof the user data via the data plane operations from the first wirelessaccess point to the second wireless access point, the redirection of theforwarding of the user data via the data plane operations to the secondwireless access point.

One or more aspects of the subject disclosure include a process thatincludes participating, by a processing system including processor, in amobile service by a first portion of a wireless network operating withina first radio frequency spectrum. The mobile service includes controloperations and data forwarding operations of the first portion of thewireless network, wherein the control operations are separate from thedata forwarding operations and configured to facilitate a forwarding ofuser data via the data forwarding operations. A second portion of thewireless network is identified, by the processing system, operatingwithin a second radio frequency spectrum, wherein the first radiofrequency spectrum comprises one of a managed frequency spectrum and anun-managed frequency spectrum, and wherein the second radio frequencyspectrum comprises a different one of the managed frequency spectrum andthe un-managed frequency spectrum. The participating in the mobileservice is requested to be transferred to the second portion of thewireless network, wherein the request is made via the control operationsand without interrupting the forwarding of the user data via the dataforwarding operations of the first portion of the wireless network. Aresponse to the request is received, by the processing system, via thecontrol operations without interrupting the forwarding of the user datavia the data forwarding operations of the first portion of the wirelessnetwork. Responsive to the response indicating that second portion ofthe wireless network has been configured to accommodate a redirection ofthe forwarding of the user data via the data forwarding operations fromthe first portion of the wireless network to the second portion of thewireless network, the redirection of the forwarding of the user data isfacilitated, by the processing system, via the data forwardingoperations to the second portion of the wireless network.

One or more aspects of the subject disclosure include a machine-readablestorage device, including executable instructions that, when executed bya processing system including a processor, facilitate performance ofoperations. The operations include accessing a network service by afirst portion of a network operating within a first wireless spectralregion, wherein the network service comprises control operations anddata forwarding operations of the first portion of the network, whereinthe control operations are separate from the data forwarding operationsand configured to facilitate a forwarding of user data via the dataforwarding operations. A second portion of the network is identifiedoperating within a second wireless spectral region, wherein the firstwireless spectral region comprises one of a managed wireless spectralregion and an un-managed wireless spectral region, and wherein thesecond wireless spectral region comprises a different one of the managedwireless spectral region and the un-managed wireless spectral region. Arequest accessing of the network service be transferred to the secondportion of the network is made via the control operations and withoutinterrupting the forwarding of the user data via the data forwardingoperations of the first portion of the network. A response to therequest is detected via the control operations without interrupting theforwarding of the user data via the data forwarding operations of thefirst portion of the network. Responsive to the response indicating thatsecond portion of the network has been configured to accommodate aredirection of the forwarding of the user data via the data forwardingoperations from the first portion of the network to the second portionof the network, the redirection of the forwarding of the user data isfacilitated via the data forwarding operations to the second portion ofthe network.

Referring now to FIG. 1, illustrative embodiments of an exemplarycommunication network for providing services to communication devices isshown. In one or more embodiments, a communications system 100 caninclude a network 150 such as a Software Defined Network (SDN), or SDNNetwork 150. The network 150 can be various types of networks, includingnetworks that utilize virtualization. The SDN Network 150 can becontrolled by one or more SDN Controllers. For example, the SDN network150 can include a manager SDN controller 130, an access SDN controller135, a Core SDN controller 140, and/or a transport SDN controller 145.The functions of the different types of SDN Controllers 130-145 arefurther described below. Each SDN controller, such as, for example andease of illustration, the manager SDN controller 130, can be provided bya computing system executing computer-executable instructions and/ormodules to provide various functions. In one or more embodiments,multiple computer systems or processors can provide the functionalityillustrated and described herein with respect to each SDN controller130-145. To simplify the description of the concepts and technologiesdescribed herein, each SDN controller 130-145 is illustrated anddescribed herein as being provided by a single computing system.However, it should be understood that this example is illustrative andtherefore should not be construed as being limiting in any way.

In one or more embodiments, each SDN controller 130-145 can includevarious components and/or can be provided via cooperation of variousnetwork devices or components. For example, each SDN controller 130-145can include or have access various network components or resources, suchas a network resource controller, network resource autonomouscontroller, a service resource controller, a service controlinterpreter, adapters, application programming interfaces, compilers, anetwork data collection and/or analytics engine. Each SDN controller130-145 also can include or access information describing availableresources and network information, such as network object statistics,events or alarms, topology, state changes. In one or more embodiment,each SDN controller 130-145 can use and/or can generate and/or accesssystem configurations, including configurations of resources availableto the manager SDN controller 130 for proving access to services.

In one or more embodiments, the communication system 100 can include aservice-supporting portion, referred to generally as a service layer125. The service layer 125 can provide access to services and/orapplications, e.g., including third-party services and/or applicationsat a higher application layer. The service layer 125 may includecapability servers, e.g., owned by or otherwise under the direction ofan operator of the communication network 100, that can access andprovide access to application layer servers, e.g., including applicationlayer servers owned by third-party content providers via open and/orsecure Application Programming Interfaces (APIs). Alternatively or inaddition, the service layer 125 can provide an interface to a coreportion of the network referred to generally as a core network. Thecommunication network 100 can also include access to applications, suchas fixed applications and mobile applications 162A-C.

In one or more embodiments, the communication network 100 can include anSDN network 150. The SDN network 150 can include one or more SDNcontrollers 130, 135, 140 and 145 that can provide different types offunctions and can be arranged in virtual layers. For example, the SDNnetwork 150 can include a manager SDN controller 130 that controls andcoordinates functioning of the SDN network 150. The manager SDNcontroller 130 can be a top-level management system in the architecture.Below the manager SDN controller 130, a next level of SDN controllers135, 140 and 145 can be instantiated and configured by the manager SDNcontroller 130 to provide specific classes of functionality in thearchitecture. For example, the manager SDN Controller 130 can providelevel-3 functionality to control and coordinate service control,configuration, and data flow in the communication network 100. Themanager SDN controller 130 can, as needed, instantiate, configure,and/or direct level-2 SDN controllers 135, 140 and 145 for controllingaccess, core, and/or transport capabilities in the communication network100.

In one or more embodiments, the SDN network 150 can allow thecommunication network 100 to separate control plane operations from adata plane operations and can enable layer abstraction for separatingservice and network functions or elements from physical networkfunctions or elements. In one or more embodiments, the manager SDNcontroller 130 can coordinated networking and provision of applicationsand/or services. The manager SDN controller 130 can manage transportfunctions for various layers within the communication network and accessto application functions for layers above the communication network. Themanager SDN controller 130 can provide a platform for network services,network control of service instantiation and management, as well as aprogrammable environment for resource and traffic management. Themanager SDN controller 130 also can permit a combination of real timedata from the service and network elements with real-time or nearreal-time control of a forwarding plane. In various embodiments, themanager SDN controller 130 can enable flow set up in real-time, networkprogrammability, extensibility, standard interfaces, and/or multi-vendorsupport. In one embodiment, interactions between layers of thecommunication network 100 can be based upon policies to determineoptimum configuration and rapid adaptation of the network 100 tochanging state and changing customer requirements for example, predicteddemand, addition of new users, spikes in traffic, planned and unplannednetwork outages, adding new services, and/or maintenance.

In one or more embodiments, each SDN controller 130-145 can instantiatea virtualized environment including compute, storage, and data centernetworking for virtual applications. For example, the manager SDNcontroller 130 can direct on-demand instantiation of network elements,such as Virtual Network Function (VNF) elements at on-demand locationsto support network services for a customer or for the autonomous networkresource controller where capacity is needed or where backup of networkelements due to failures. Service functions can be moved and/or changedin response to traffic flow rather than traffic flow moving to thedesired service functions.

In one or more embodiments, the manager SDN controller 130 can cooperatewith a cloud orchestrator in instantiating level-2 SDN controllers135-145 and network services to support the network configuration inconnecting Virtual Machined (VMs) that the cloud orchestrator is settingup. The network instantiation and configuration can includeconfiguration of the virtual networks, which may operate at variousphysical levels in a cloud server architecture, including hypervisor,top of rack, cloud network fabric, and/or IP provider edge, which canconnect the cloud network with the service provider WAN network. In oneor more embodiments, the level-2 SDN Controllers 135-145 can cooperatewith a cloud orchestrator in instantiating VNF elements for use in, forexample, the Core Network.

In one or more embodiments, a communication device 116 can operate incommunication with and/or as a part of a communications network 100. Thefunctionality of the communication device 116 may be provided by one ormore server computers, desktop computers, mobile telephones,smartphones, laptop computers, set-top boxes, other computing systems,and the like. It should be understood that the functionality of thecommunication device 116 can be provided by a single device, by twosimilar devices, and/or by two or more dissimilar devices. For purposesof describing the concepts and technologies disclosed herein, thecommunication device 116 is described herein as a workstation orpersonal computer. It should be understood that this embodiment isillustrative, and should not be construed as being limiting in any way.

The communication device 116 can execute an operating system and one ormore application programs. The operating system can be a computerprogram that controls the operation of the communication device 116. Theapplication programs can be executable programs that are configured toexecute on top of the operating system to provide various functions.According to various embodiments, the application programs can includeweb browsers, productivity software, messaging applications,combinations thereof, or the like. In one or more embodiments, theapplication programs of the communication device 116 can includeapplications that enable interactions between the communication device116 and other devices or entities. In some contemplated embodiments, theapplication programs can provide functionality for interacting withand/or communicating with the communication network 100 and, in turn,having communications analyzed by the manager SDN controller 130 or,alternatively, any of the SDN Controllers 130-145 in the SDN network150.

According to various embodiments, the SDN network 150 can include and/oraccess resources, such as a service orchestrator, a software definednetwork controller, a cloud orchestrator, and/or other elements. Itshould be understood that the manager SDN controller 130, and any of theabove-described components, or combinations thereof, may be embodied asor in stand-alone devices or components thereof operating as part of orin communication with the communication network 100. As such, theillustrated embodiment should be understood as being illustrative ofonly some contemplated embodiments and should not be construed as beinglimiting in any way.

In one or more embodiments, the SDN network 150 can automaticallyevaluate application service requirements that have been requested fromthe communication system 100. In one embodiment, a service request canbe received from a subscriber, or customer, or customer device. Forexample, a request can be receive via a portal. The service request canbe provided to the soft manager SDN controller 130 for service creation,instantiation, and management. According to various embodiments, theservice request can be analyzed by the manager SDN controller 130. Inone embodiment, the manager SDN controller 130 can access or query theservice layer 125 to determine service requirements needed forfulfilling the service request.

In one or more embodiments, a service request can be received byequipment of a subscriber or customer (e.g., via the portal), andprovided to the SDN network 150 for service creation, instantiation, andmanagement. The service request can include application objects and/orrequests for particular services or functions. Thus, the service requestcan include objects that define service functions that are desired,requests for generation of services and/or requests for particularfunctionality, queries, combinations thereof, or the like. It should beunderstood that these examples are illustrative and therefore should notbe construed as being limiting in any way. According to variousembodiments, the service request can be analyzed by the SDN controller130-145 and a set composed of a directed graph and the associated modelor model files are selected. The model can define features of theservice and can generate in a programming language or format such asXML, Yang models, other types of files, combinations thereof, or thelike. The selected directed graph can be used at runtime to fill in theevent-specific details from the API, the resource allocations per thedirected graph and the resource model, and one or more state changes inthe network through the adapters.

In one or more embodiments, the communication device 116 can communicatewith the communication network 100 via a wireless communication link.For example, the communication device 116 can be a mobile communicationdevice 116 that communications via a cellular communication link througha Radio Access Network (RAN) technology. A mobility network 117, such asa 3GPP wireless network, e.g., an LTE network or a 5G network, canestablish wireless communications with the communication device 116,where the communication device 116 can move from cell to cell, whilemaintaining a communication session. In another example, thecommunication device 116 can communication with the communicationnetwork via a non-3GPP wireless link, e.g., a WiFi network link. TheWiFi network can be, for example, a local area network (LAN) that issupported by a router capable of wireless communications or can be anindividual device, such another mobile communication device 116 capableof acting as an intermediary (e.g., a Hot Spot). In one or moreembodiments, the communication network 100 can be a converged networkcapable of supporting a wide range of access, core and transportnetworks, such as wireline, wireless, satellite, 3GPP, non-3GPP, and/or5G. It is understood that the radio frequency spectrum used in wirelessaccess can include licensed spectrum, unlicensed spectrum andcombinations thereof.

In one or more embodiments, a Management Gateway (MGW) 142 can beincluded in the communication network 100. The MGW 142 can capturetraffic entering the communication network 100 from variouscommunication devices 116 and/or various Access Networks (AN) 117. TheMGW 142 can communicate with the SDN network 150, e.g., with the managerSDN controller 130, regarding traffic entering the communication network100. In one embodiment, the MGW 142 and the manager SDN controller 130can communicate via a communications protocol, such as an OpenFlow®protocol that provide access to a forwarding plane of a network device,such as a switch or router, over a network. OpenFlow® is a registeredtrademark of the Open Networking Foundation of Palo Alto, Calif. The MGW142 can inform the management SDN controller 130 of informationregarding services sought by one or more communication devices 130. Themanagement SDN controller 130 can analyze these services to determineservice functions and/or network data flows that would be required tofacilitate delivery of these services to the communication devices 116.

In one or more embodiments, the manager SDN controller 130 can query theservice layer 125 to determine the functional and/or resourcerequirements to provide the service to the communication device 116. Inone or more embodiments, the service requirements can include servicefeature data. In one or more embodiments, this service feature data canbe generated by or provided to the service layer 125 and/or the managerSDN controller 130 via interactions between the communication device 116and the portal. For example, in the process of making the servicerequest, the communication device 116 can make a series of selectionsfrom menus, drop-down lists, fields, tables, or other data or objectselection mechanisms that may be provided by the portal and/or theapplication programs executing on the communication device 116. In someembodiments, the application programs can include a web browserapplication and/or other application that can obtain data from theportal. In one or more embodiments, the application programs can use thedata to generate and present a user interface at the communicationdevice 116. The user interface can include possible service features,and a user or other entity can select the desired features, drag anddrop desired features, and/or otherwise indicate desired features in aservice.

In one or more embodiments, the manager SDN controller 130 can analyzepolicies or policy defined for a service. This policy can includenetwork engineering rules, which can be defined by a network designer,engineer, business unit, operations personnel, or the like, or asubscriber policy, which can be defined during ordering of the service.Subscriber policies can include, for example, service level agreements(“SLAs”), location restrictions (e.g., locations at which the servicesare allowed or not allowed), bandwidth ranges, time restrictions (e.g.,times of day, days of week, or other times at which the service isallowed or not allowed), security restrictions or policies, combinationsthereof, or the like.

In one or more embodiments, the manager SDN controller 130 can determinefrom the service model one or more physical network functions or otherresources that will be needed or used to support the service. Themanager SDN controller 130 also can analyze the service model toidentify one or more virtual network functions or other functions thatwill support or provide the features of the service. The manager SDNcontroller 130 also can determine, via analysis of the service model,process flows between the various resources and/or functions used tosupport or provide the service features.

In at least some embodiments, the SDN network 130 implements a multiplelevel, dynamic design by which the manager SDN controller 130 of the SDNnetwork 150 can automatically prioritize and instantiate a next lowerlevel (e.g., level-2) SDN controller including one or more of an accessnetwork SDN controller 135, a core network SDN controller 140, and/or atransport network SDN controller 145. It is understood that such actionscan be undertaken on the fly, e.g., at runtime, responsive to networkactivity, responsive to particular requests, in a course of normalnetwork operations, configuration, management, and the like. Generally,the manager SDN controller 130 can instantiate at least one set of theselevel-2 SDN controllers 135-145 to provide baseline functionality andconnectivity for a least one communication device 116. As serverrequests are processed, the manager SDN controller 130 can evaluate theservice request requirements, i.e., the service features, and comparethe required resources and capacities for these resources with theresources and capacities currently available at the SDN network 150 viathe level-2 SDN Controllers 135-145.

In one embodiment, the manager SDN controller 130 can communicate witheach of the instantiated SDN controllers 135-145 via a communicationinterface, such as an interface that applies OpenFlow® data networkprotocols. In addition, the SDN controllers 135-145 of level-2 to cancommunicate among themselves to determine resource capabilities,capacities, shortages, failures, and/or warnings. In one or moreembodiments, if the manager SDN controller 130 determines that therequested service can be performed, within system margins, using thecurrently instantiated SDN controllers 135-145, then the manager SDNcontroller 130 can decide to direct the SDN controllers 135-145 toperform the service for the communication device 116. Alternatively, ifthe manager SDN controller 130 determines a shortage or shortfall in aneeded resource, then the manager SDN controller 130 can directinstantiation of one or more new SDN controller 135-145 to perform allor part of the requested service. For example, the manager SDNcontroller 130 may determine that the service request associated withthe example communication device 116, or many communication devices 116,or merely received at the communication network 110 from anindeterminate device (e.g., a request for resources from anothernetwork) requires additional core SDN controller capacity 140. In thiscase, the manager SDN controller 130 can direct the instantiation ofadditional core SDN controller 140 capacity from a set of configurableSDN controller devices at the cloud.

In one or more embodiments, level-2 SDN Controllers 135-145, includingaccess SDN controller 135, core SDN controller 140, and transport SDNcontroller 145 can control devices at an upper level, e.g., level-1, ofthe communication network 100. For example, the access SDN controller135 can control, direct, configure, and monitor access resources 117 and119 for the network 100, such as eNodeB controllers, RAN controllers,and or WiFi controllers. In another example, the core SDN controller 140can control, direct, configure, and monitor core resources 174A-176C forthe core network of the communication network 100, such as Gateways (GW)for Control Plane (CP) 174A-C, User Plane (UP) 176A-C, and/or legacy(i.e., combined user and control plane). In another example, thetransport SDN controller can control, direct, configure, and monitortransport layer services 154, such as a Multiprotocol Label Switching(MPLS) network, Fiber Optics network, and/or a Backbone network.

In one or more embodiments, the manager SDN controller 130, adapted tosupport level-3 functionality, can manage one or more sets of level-2SDN controllers 135-145 in the SDN network 150. The manager SDNcontroller 130 can configure and/or reconfigure the instantiated SDNcontrollers 135-145 to optimize the SDN network 150 according to loadingcreated by the service requests. For example, the manager SDN controller130 can invention automatically instantiate multiple levels of fullydistributed SDN controllers 135-145. Likewise the level-2 SDNcontrollers 135-145 can instantiate and/or configure and/or reconfigureVNF elements 174A-176C at level-1. Each of the SDN controllers 130-145can support instantiation “on the fly” based on new requests, the endingof old requests, monitoring network traffic, and/or requesting loadinginformation from any of the other SDN controllers 135-145 and/or the VNFelements 174A-176C.

For example, the manager SDN controller 130 can instantiate and/ordecommission SDN controllers 135-145 into and out from the SDN network150 on an on-going basis according to the exchange-to-exchange (E2E)application service requirements. Similarly, the SDN controllers 135-145can instantiated and/or decommission and/or reconfigure VNF elements174A-176C. For example, in a streaming media application, such as aNetflix™ Video Delivery application, the manager SDN controller 130 candetermine that network demands for the access SDN controller 135 andtransport SDN controller 145 may be relatively large for a given set ofcommunication devices 116, while the core SDN controller 140 demands forthese communication devices 116 may be relatively normal. The managerSDN controller 130 can look at the available resources and capacitiesfor the currently instantiated SDN controllers 135-145 that are supportthese communication devices 116. If the demands of the media streamingapplication exceed the available resources, then the manager SDNcontroller 130 can automatically address the issue by, for example,instantiating additional access SDN controller 135 and transport SDNcontroller 145 resources.

In one or more embodiments, the manager SDN controller 130 may determinethat sufficient resources exist at the currently instantiated access SDNcontroller 135 and transport SDN controller 145 resources, however, thepriorities of these resources need to be adjusted. For example, where aheavy streaming media loading is identified, the access SDN controller135 and transport SDN controller 145 resources may be given higherpriority in comparison to the core SDN controller 140. Conversely, if aheavy loading of Voice over IP (VoIP) services is identified, then themanager SDN controller 130 can automatically place the core network SDNcontroller 140 into higher priority in comparison to access network SDNcontroller 135 and transport network SDN controller 145.

In one or more embodiments, a SDN-controlled network, using networkfunction virtualization, software defined networking, and/or cloud-basedconcepts, can provide flexibility in number, type and/or configurationof virtual networks, sometimes referred to as flexible network slicing.Network slicing facilitates distributed functionality, e.g., to supportdiverged types of services and requirements, such as those supportingfuture developments in wireless networks including 5G networks. SDNcontrollers 130 can provide control and configuration to supportdifferent network slices on appropriate network slices or clouds 162A-Cby instantiating and controlling a proper sets of VNF elements 174A-176Cand by the optimal distribution of these VNF elements 174A-176C based onapplication and service requirements.

Generally speaking, network slicing is a network management technique inwhich compute and/or connectivity resources in a communications networkare divided to create a set of different virtual networks. For example,network slices can be supported by virtual network functionsinstantiated upon generic computing resources to provide specificnetwork functions. Without limitation, network slices can be used in oneor more of a core network, a radio access network, a backhaul network.Isolation provided by the network slices can be applied to differentoperators, different types of services, different types of networktraffic, different users and/or classes of users, and the like.

In one or more embodiments, network slicing can be used by the SDNnetwork to support multiple virtual networks behind the air interface(s)117 of the communication network. The slicing of the network intomultiple virtual networks can provide optimal support for differentRadio Access Networks (RAN) and/or different service types runningacross a single RAN. Further, in one or more embodiments, flexibledistribution of the access, edge, and core elements of the network cloudcan provide optimal support regarding latency and/or service isolationfor different apps and service requirements. Connectivity betweencomputing resources can be allocated so that traffic of one slice can beisolated from that of another. Isolation can be based on one or more ofnetwork operator, service, application, user, user equipment, level ofsubscription service, and so on. By way of example, one slice can beconfigured to suit the needs of a Machine Type Communication (MTC)service, which typically generate large numbers of short transmissionsthat do not require ultra-reliable connections. Another slice cansupport Mobile Broadband (MBB), or enhanced Mobile Broadband (eMBB)services, having different requirements. Network slices created to servethe needs of different services may be built upon the resourcesallocated to a network operator within a slice that isolates the networkoperator from other network operators on a set of resources associatedwith a service provider.

In one or more embodiments, the SDN Network 150 can determine whatservice(s) is being used and which external network and/or networkoperator, e.g., by way of an Access Point Node (APN), is being used forthe specific traffic. In one embodiment, the analysis can be performedby a SDN controller 130-145, which derive information either directlyfrom communications entering the network 100 form one or morecommunication devices 116 or from a MGW 142 that is monitoring this typeof traffic. In one or more embodiments, a SDN Controller 130 can performanalysis that determine a detailed granularity of the specific servicesbeing sought by or provided to the communication device 116. Thisdetailed granularity can reveal sets of service functions (e.g.,identifying servers, providing connections to applications, verifyingauthenticity, providing control plane and user plane functions) that arenecessary for facilitating the delivery of services. The detailedgranularity can also include determining various data pathways, withinthe network 100 and beyond, necessary for facilitating the delivery ofservices. The SDN Controller 130 can instantiate VNF elements 174A, 176Athat can cause traffic to be sent to respective destinations such as 4G,4G+, or 5G APNs, based upon breaking up the specific services requestedinto the types of service functions, resources, data accesses, and/ornetwork data paths. The VNF elements that are composed, configured, andchained by the SDN Controller 130 for implementing the necessary servicefunctions are, in turn, instantiated into the 5G network 100 in networklocations that optimize one or more characteristics of the servicefunctions and/or network data paths.

Examples of flexible, adaptive networks, such as the illustrativeexample communication network 100, are disclosed in commonly owned, U.S.patent application Ser. No. 15/344,692, entitled “Method and Apparatusfor a Responsive Software Defined Network,” filed on Nov. 7, 2016, andincorporated herein by reference in its entirety. Additionally,techniques related to dynamic network routing in a software definednetwork are disclosed in U.S. patent application Ser. No. 15/351,618,entitled “Method and Apparatus for Dynamic Network Routing in a SoftwareDefined Network,” filed on Nov. 15, 2016, and also incorporated hereinby reference in its entirety.

FIG. 2 depicts an illustrative embodiment of another examplecommunication network 200 for providing services to mobile communicationdevices, such as user equipment (UE) 202. The UE 202 can include anymobile device capable of accessing a service via a mobile operator'snetwork, such as mobile phones, tablet devices, laptop computers,desktop computers, electronic gaming devices, including game consolesand/or game controllers, and the like. More generally, the UE 202 caninclude any device configured to support Internet protocol networkcommunications. In at least some embodiments, the UE 202 can includemachine type communications, e.g., machine-to-machine communications(M2M) according to the Internet of Things (IoT), including vehicles,smart meters, residential appliances, industrial equipment, and thelike.

The communication network 200 includes a mobile operator's network 201having a first radio access network 204 and a mobile core network 212.In the illustrative example, the first radio access network 204 operatesaccording to a 3GPP protocol, such as 2G, 3G, 4G, LTE, and/or 5G. In atleast some embodiments, the first radio access network 204 operateswithin a managed portion of the radio frequency spectrum, which in atleast some applications, can include licensed portions and/or unlicensedportions of the radio frequency spectrum.

In the illustrative embodiment, the first radio access network 204includes an evolved Node B (eNodeB) 206. The eNodeB 206 terminates oneend of a wireless radio frequency link with the UE 202. The eNodeB 206is in communication with the core portion of the mobile service providernetwork 212, such as an evolved packet core, that process packet flowsassociated with one or more services accessed by the UE 202. In general,the UE 202 can be connected to the mobile service provider network 201via different accesses simultaneously, e.g., sending and receivingdifferent IP flows through different accesses. It is understood thatdifferent services can include different characteristics, e.g., in termsof QoS requirements, bandwidth, access restrictions, and/or policies.

By way of non-limiting example, services can include video telephonycalls, media file synchronizations, e.g., a podcast and downloading ofTV series, non-conversational video streaming, e.g., IPTV, and/orPeer-to-Peer (P2P) downloads. It us further understood that some of thepacket flows of the services may be from the same application. One ormore of the packet flows can be accommodated over 3GPP access, whereas,others of the one or more packet flows can be accommodated over non-3GPPaccess. Details related to multi access PDN connectivity and IP flowmobility are disclosed in 3GPP TR23.861, entitled “Network Based IP FlowMobility,” Rel. 13, incorporated herein by reference in its entirety.

The Evolved Packet Core (EPC) 212 can include one or more of a MobilityManagement Entity (MME) 214, a Serving Gateway (S-GW) 216, first andsecond PDN Gateways (P-GW) 218 a, 218 b, generally 218, a HomeSubscriber Server (HSS) 217, and an Authentication and AccessAuthorization (AAA) server 218. In at least 3GPP Long Term Evolution(LTE) applications, the MME 214 is involved in beareractivation/deactivation, in choosing an SGW 216 at the initial attach ofthe UE 202. The MME 214 also participates in authenticating a user ofthe UE 202, e.g., by interacting with the HSS 216, and by providingcontrol plane functionality for mobility, e.g., between LTE, 5G, and2G/3G access networks. The SGW 216 routes and forwards user datapackets, while also acting as a mobility anchor for a user plane duringinter-eNodeB handovers and as the anchor for mobility between LTE andother 3GPP technologies.

The P-GW 218 provides connectivity from the UE 202 to external packetdata networks by providing a point of exit and entry of traffic for theUE 202. In the illustrative example, the external data networks includean administrative packet data network 222 and one or more servicespacket data networks 226. Examples of service packet data networks 226include, without limitation, the Internet and/or other unified messagingsystems, universal media services, and the like. In at least someembodiments, the UE 202 can have simultaneous connectivity with morethan one PGW 218 for accessing multiple PDNs.

The HSS 217 provides a central database that contains user-relatedand/or subscription-related information. The HSS 216 can providefunctionalities that support one or more of mobility management, calland session establishment support, user authentication and accessauthorization.

In general, mobile data can be carried over either 3GPP networks,non-3GPP networks or combinations thereof. The example communicationsnetwork includes a second radio access path 208. The second radio accesspath 208 includes a non-3GPP wireless access terminal 210. It isunderstood that the non-3GPP wireless access terminal 210 can supportwireless communications in unlicensed portions of the radio frequencyspectrum. For example, a non-3GPP network 208 can include a wirelessaccess terminal 210 according to one or more of a WiFi local areanetwork, WIMAX, Bluetooth personal area network, and more generally anyone or more of the IEEE 802.XX wireless networks.

In some embodiments, the non-3GPP access path 208 provides a trustedaccess path. Examples of trusted non-3GPP access paths can include amobile carrier's own installed WiFi access points 210. In these paths,user authentication can be performed in the same or similar manner as in3GPP network authentication, e.g., using SIM card data. Alternatively orin addition, the non-3GPP access path 308 can include non-trusted accesspaths. Examples of non-trusted access paths include public wireless LANsand/or domestic WiFi hotspots. Such public WiFi hotspots may connect toother packet data networks, such as the Internet without utilizing themobile provider network 201. It is understood that in at least someembodiments, security can be assured by establishing an IPsec tunnelbetween the UE 202 and the ePDG 220.

The EPC 212 includes an Evolved Packet Data Gateway (ePDG) 220 givesmobile network operators the ability to deliver mobile services overuntrusted, non-3GPP network access, which could include residential,public, and enterprise Wi-Fi hotspots. The ePDG 220 can provide networksecurity and/or authentication of mobile devices 202 within theoperator's network 212. Alternatively or in addition, the ePDG 220 canprovide secure connections with the UE 202 over the untrusted, non-3GPPaccess network 208. Details of the network elements are disclosed in3GPP TS 23.402, entitled “Architecture Enhancements for Non-3GPPAccess,” Rel. 12, are incorporated herein by reference in its entirety.

In some embodiments, the mobile provider network 201 includes an Accessnetwork Discover & Selection Function (ANDSF) 224. The ANDSF 224 can beconfigured to manage a list of access networks available in a vicinityof the UE and for storing and managing status reports from the UE 202,e.g., providing UE location and profile.

In the illustrative embodiment, the UE 202 can access a first service,including a packet flow 203 between the UE 202 and equipment of theservice provider, and/or other network accessible equipment. In at leastsome embodiments, the service includes a packet flow 203 between the UE202 and one or more other UEs (not shown), e.g., as in a P2P exchange,e.g., streaming audio and/or video, a VoIP call, and the like. Themobile provider network 201 can include slicing capabilities asdisclosed herein, such that at least a portion of the packet flow 203 ofthe first service is supported by a first slice 220 a that may beassociated with a first mobile application used in cooperation withdelivery of the service to the UE 202. The mobile provider network 201can include one or more other slices, such as a second slice 202 b. Thesecond slice 202 can be configured to facilitate delivery of the serviceto the UE 202, wherein the service includes the first application and/ora second application that may be associated with the same service. In atleast some embodiments, the service can be supported by either one ofthe slices 220 a, 220 b alone or in combination. it is furtherunderstood that allocation and/or modification of the slices 220 a, 220b can be commissioned, configured, re-configured and/or decommissionedaccording to the disclosure of U.S. patent application Ser. No.15/590,648, entitled “Multi-Slicing Orchestration System and Method forService and/or Content Delivery,” having been assigned attorney docketNo. 2016-1940_7785-1593, which is incorporated herein by reference inits entirety.

FIG. 3A depicts an illustrative embodiment of a process 300 used inportions of the system described in FIGS. 1 and 2. The process 300 canfacilitate a dynamic slice switching and/or handover between 5G 3GPP andnon-3GPP networks.

The UE 202 (FIG. 2) accesses a mobile service via a first access pointat 302. The mobile service includes separate packet data exchangesaccording to a control plane and a user plane, wherein the control planeand the user plane are associated with the mobile service. The firstaccess point can be a 3GPP access point, such as the eNodeB 206. It isunderstood that any of the 3GPP access points can include 5G accesspoints 117 (FIG. 1), e.g., in communication with a management gateway142 a service layer network or cloud 125 and/or an SDN controller130-145. In some embodiments, the UE 116, 202 initially attaches to the3GPP access point 117, 206. Alternatively or in addition, the UE 116,202 is handed over to the 3GPP access point 117, 206, e.g., based on oneor more of mobility of the UE 202, a condition of the mobility network,a requirement of the service, a mobile network provider and/or userpreference and so on.

Alternatively or in addition, the first access point can be a non-3GPPaccess point, such as the example WiFi access point 210. The non-3GPPaccess point can include managed and/or unmanaged non-3GPP access points210 configured to access the ePGD 220, to support access to mobileprovider network 210 services and/or third party services by way of themobile provider network 210. Access can include authorization, e.g., byway of the AAA server 218, and identification of subscriber informationavailable by way of the USS server 217. Similarly, the UE 116, 202initially attaches to the non-3GPP access point 210. Alternatively or inaddition, the UE 116, 202 is handed over to the non-3GPP access point210, e.g., based on one or more of mobility of the UE 202, a conditionof the mobility network, a requirement of the service, a mobile networkprovider and/or user preference and so on.

A second access point is identified at 304. The second access point canbe identified by the UE 202. For example, the UE 202 may detect awireless signal from the second access point by which one or more of anidentity, a location, a type, a provider, a security level, a wirelessaccess technology, and the like. Alternatively or in addition, the UE202 can receive a message and/or similar notification from the networkservice provider and/or a third party that the second access point isavailable. For example, the network service provider can determine alocation of the UE 116, 202 and/or a performance parameter of the secondaccess point obtained by the UE and reported to the network serviceprovider.

It is understood that identification of the second access point caninclude identification according to the same wireless access technologyor a different wireless access technology. For example, a UE 116, 202engaging a service by way of a 3GPP access network can identify asecond, non-3GPP access network. Alternatively, the UE 116, 202 engaginga service by way of a non-3GPP access network can identify a second 3GPPaccess network. Non-3GPP access networks can include those managed bythe mobile network provider and others not managed, e.g., public,domestic and/or enterprise WiFi.

An evaluation of the second access point is performed in view of themobile service at 306. For example, the UE 116, 202 can determinewhether a dynamic slice switching and/or a handover should be requestedfrom the first access network to the second. Alternatively or inaddition, equipment of the mobile network provider and/or a third party,such as an access management provider, can make a similar determination.Such determinations can be based on one or more of a subscription levelof a user of the UE 116, 202, an equipment type of the UE 116, 202,e.g., whether the device includes the appropriate hardware, radio,antenna, and/or software, a condition of the network, e.g., congestion,delay, service outages current or planned, and the like. Alternativelyor in addition, such determinations can be based on a required QoS ofthe engaged and/or requested service, a subscribed and/or authorized QoSof the subscriber, past performance, e.g., whether the same or similartype of UE was granted the same or similar change, e.g., in associationwith the same or similar service, e.g., during the same or similarnetwork conditions, UE conditions, and so on. In at least someembodiments, such determinations can be based on mobility of the UE,whether the UE is moving, whether it is moving fast or slow, and so on.

A determination as to whether a change should be requested is made 308.In at least some embodiments, the determination can be based on any oneor more of the aforementioned evaluations. Likewise, the determinationcan be based on a user profile, e.g., including a preference for aparticular access network and/or network slice.

The UE 116, 202 requests a change to second access point at 310. Therequest can be forwarded from the UE 202 by way of an existing controlplane and/or existing data plane packet exchange. For LTE applications,the request can be forwarded by way of the standard bearer and/or by waya dedicated bearer associated with the service. For 5G applications, therequest can be forwarded by way of a default slice and/or by way of aslice allocated to the service. Alternatively or in addition, therequest is forwarded to a controller of the mobile network providerand/or a third party managing slice switching and/or handovers. In atleast some embodiments, the change request message is made according toa protocol that identifies the message type as being a change request.Alternatively or in addition, the change request message can beaddressed to a particular network entity, such as the slice changeand/or handover controller.

Equipment of the mobile network provider and/or equipment of a thirdparty managing the slice switching and/or handovers receives therequest. In at least some embodiments, the received request is evaluatedto determine whether the request can or otherwise should be satisfied.The evaluation can be based on one or more of several considerations.Considerations include, without limitation, an identity of thesubscriber and/or the UE device, an identity of other subscribers and/orequipment, e.g., other UE devices participating in the service, e.g., acalling party and a called party of a VoIP call, a QoS based on asubscription, a QoS requirement of the service and/or applications usedby the service, network conditions, e.g., network congestion, delays,bandwidth, and so on. In at least some embodiments, the evaluation isbased at least in part on an SLA of a subscriber of the requesting UEand/or subscribers of other UEs participating cooperatively in theservice with the UEs, e.g., SLAs of the calling and/or called parties.

To the extent that the request is permitted, the network alone or incooperation with equipment of a third party, such as equipment of athird party service provider providing the service and/or equipment ofthe third party managing slice switching and/or handovers, thealternative access network can be instantiated, accessed, configuredand/or reconfigured as necessary to accommodate the request. In thisregard, message are exchanged by the control plane between one or moreof the requesting UE, the mobile network, any participating third partyequipment and/or other UEs engaging cooperatively in the service. Thenetwork and/or third party equipment can provide a message to therequesting UE based on results of the aforementioned evaluation. Inparticular the related exchanging of the control plane messages canoccur without interrupting user data packets or traffic associated withthe service. Based on the message exchange, the second network isestablished and a notice sent to the requesting UE.

The requesting UE can determine whether the request has been accepted at312, e.g., based on the received message. To the extent the change isaccepted, the UE performs any reconfigurations as may be necessary toaccess the second network. Changes can include, without limitation,activation of another antenna and/or radio, e.g., a first antenna and/orradio used by the first access network and a second antenna and/or radioused by the second network. Once the reconfiguration has beenaccomplished, the UE can transfer packet exchanges, e.g., control planeand/or data plane packet exchanges to the second access network at 314.

It is understood that the process 300 can be repeated as may benecessary. For example, a request granted based on then current networkconditions may be re-directed to the first access network and/or yetanother access network based on a change in conditions.

To the extent that a subscription, e.g., a subscriber SLA, does notallow or permit a requested change that would be otherwise granted, theprocess can include steps to facilitate a change to the subscriptionand/or subscriber SLA. For example a change request for destinationsubscriber SLA can be received dynamically, e.g., during delivery of arelated service. The request can occur when a calling party, eitherprior to a call or while talking to the called party can, receivescoverage and from the HSS, calling party and/or recipient partysubscriber profile identities, and/or class or types, and/or QoS classesfor the calling party and/or recipient subscriber. The callingsubscriber UE and/or the recipient subscriber UE can dynamically pay fora change or increase to the calling party and/or the called party SLAsand even moving the call to a superior Slice for better connection.Namely one party can request and/or pay for a change to their own SLAand/or the SLA of the other party.

That requested change to the SLA can be applied to the specific callonly. Alternatively or in addition, the change to the SLA can be appliedfor a certain period of time, for a selective user or group of users, inassociation with a special event, associated with a specific location orregion, during a specific time-of-the-day or time period of the day, dayof the week, and/or in association with or otherwise responsive to anemergency. It is understood that SLA changes can be applied to anindividual and/or a group, such as in association with a family plan,members of an enterprise network and the like.

By way of illustrative example, a reporter using her mobile UE talkingto a private subscriber and can, while talking, pay for a premiumservice/connection in 5G network. The premium service may be used toallow for streaming video and/or high quality streaming video. Suchaccess scenarios can be applied to situations in which the initiating orcalling party, i.e., the reporter, does not have access to a securenetwork, or would prefer to conceal content of user data exchanges fromother network carriers, other third parties, and the like.

FIG. 3B depicts an illustrative embodiment of a second process 350 usedin portions of the system described in FIGS. 1 and 2. The second process350 can be applied to network equipment and/or equipment of thirdparties participating in slice switching and/or handovers between 3GPPand non-3GPP networks. To this end, delivery of a first service isfacilitated to a UE via a first access network or first access point at352. The service can include, without limitation, any service accessibleto the UE, including any of the example services disclosed herein.

A request to provide the UE with access to a second access point isreceived at 354. The request can be received from the UE and/or fromanother device, such as another UE, a portal, another network device,equipment of a third party, and the like. The request is evaluated at356. As disclosed above in relation to the first process 300, therequest can be evaluated to determine whether it can or otherwise shouldbe satisfied. The evaluation can be based on one or more of severalconsiderations including, without limitation, an identity of thesubscriber and/or the UE device, an identity of other subscribers and/orequipment, e.g., other UE devices participating in the service, e.g., acalling party and a called party of a VoIP call, a QoS based on asubscription, a QoS requirement of the service and/or applications usedby the service, network conditions, e.g., network congestion, delays,bandwidth, and so on. In at least some embodiments, the evaluation isbased at least in part on an SLA of a subscriber of the requesting UEand/or subscribers of other UEs participating cooperatively in theservice with the UEs, e.g., SLAs of the calling and/or called parties

A determine is made at 358 as to whether the request is acceptable. Thedetermination can based on predetermined logic, e.g., a comparison ofany of the foregoing considerations to predetermined value, threshold orrange. Alternatively or in addition, the determination can be based onresults of prior requests, e.g., the same or similar requests from thesame or similar UE devices and/or in association with the same orsimilar service. For example, artificial intelligence can be appliedwith a goal of improving servicing of the requests. In some scenarios, arequest may appear acceptable, but based on prior experiences, may bedeemed unacceptable. To the extent the request is unacceptable, therequest is denied at 360. Processing can continue from step 354, e.g.,monitoring for and/or receiving subsequent requests at 354.

To the extent that the request is determined or otherwise deemedacceptable at 356, a pre-coordination is conducted at 362 of delivery ofthe service and/or related applications to UE via the second accessnetwork and/or access point. As disclosed in relation to the firstprocess, the pre-coordination can include an exchange of one or moremessages using a control plane associated with the service withoutinterrupting a flow of user data by the separate but related user planeof the same service.

The mobile network, the service provider and/or third party can evaluatealone or in combination, whether the requested access to the secondaccess network/point has been established and is ready to accommodateuser data traffic of the service. Responsive to a determination that thesecond access network/point is ready, a notification is provided to theUE at 364 indicating that service delivery via second access point hasbeen pre-coordinated.

Progress of the UE efforts to access the second access network/point ismonitored at 366. For example, an indication that access has beenobtained can include an exchange of a control message on a control planevia the second access network/point, indicating that the user data planeof the second access network/point is ready. A ready indication caninclude an indication that the second access network/point is availableand ready to exchange user data traffic.

A determination as to whether a dynamic slice has been switched and/orwhether the 5G 3GPP/non-3GPP handover has been completed is monitored at368. To the extent that an indication of a successful switch/handoverhas not been detected at 366, the monitoring can continue at 364. It isenvisioned that a number of attempts and/or time period may be applied,such that after a threshold number of attempts and/or time period hasbeen exceeded, the processing of the request is abandoned. Suchabandonment can include a reversion to the first access network/point,e.g., without having interrupted the user data traffic using the firstaccess network/point.

To the extent that an indication of a successful switch/handover has notbeen detected at 366, delivery of service to UE is facilitated viasecond access point at 370. This can include redirection of user planetraffic and control plane traffic from the first slice and/or accessnetwork/point to the second slice and/or access network/point.

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIGS. 3A and3B, it is to be understood and appreciated that the claimed subjectmatter is not limited by the order of the blocks, as some blocks mayoccur in different orders and/or concurrently with other blocks fromwhat is depicted and described herein. Moreover, not all illustratedblocks may be required to implement the methods described herein.

FIG. 4 depicts an illustrative embodiment of a communication system 400for providing various communication services, such as delivering mediacontent. The communication system 400 can represent an interactive medianetwork, such as an interactive television system (e.g., an InternetProtocol Television (IPTV) media system). Communication system 400 canbe overlaid or operably coupled with the communication networks 100, 200of FIGS. 1 and/or 2 as another representative embodiment ofcommunication system 400. For instance, one or more devices illustratedin the communication system 400 of FIG. 4, accesses a service by a firstnetwork operating within a first wireless spectrum, wherein the serviceincludes control and data forwarding operations of the first network areseparate and configured to facilitate forwarding of user data via thedata forwarding operations. A second network is identified operatingwithin a second wireless spectrum. A request that the accessing of thenetwork service be transferred to the second network is made withoutinterrupting the forwarding of the user data. A response to the requestis detected via the control operations, also without interrupting theforwarding of the user data. Responsive to an indication that the secondnetwork has been configured to accommodate a redirection of theforwarding of the user data from the first network to the second, theredirection is facilitated.

In one or more embodiments, the communication system 400 can include asuper head-end office (SHO) 410 with at least one super headend officeserver (SHS) 411 which receives media content from satellite and/orterrestrial communication systems. In the present context, media contentcan represent, for example, audio content, moving image content such as2D or 3D videos, video games, virtual reality content, still imagecontent, and combinations thereof. The SHS server 411 can forwardpackets associated with the media content to one or more video head-endservers (VHS) 414 via a network of video head-end offices (VHO) 412according to a multicast communication protocol. The VHS 414 candistribute multimedia broadcast content via an access network 418 tocommercial and/or residential buildings 402 housing a gateway 404 (suchas a residential or commercial gateway).

The access network 418 can represent a group of digital subscriber lineaccess multiplexers (DSLAMs) located in a central office or a servicearea interface that provide broadband services over fiber optical linksor copper twisted pairs 419 to buildings 402. The gateway 404 can usecommunication technology to distribute broadcast signals to mediaprocessors 406 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 408 such as computers or televisionsets managed in some instances by a media controller 407 (such as aninfrared or RF remote controller).

The gateway 404, the media processors 406, and media devices 408 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, Zigbee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 406 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 429 can be used in the mediasystem of FIG. 4. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 400. In thisembodiment, signals transmitted by a satellite 415 that include mediacontent can be received by a satellite dish receiver 431 coupled to thebuilding 402. Modulated signals received by the satellite dish receiver431 can be transferred to the media processors 406 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 408. The media processors 406 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 432 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 433 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system400. In this embodiment, the cable TV system 433 can also provideInternet, telephony, and interactive media services. System 400 enablesvarious types of interactive television and/or services including IPTV,cable and/or satellite.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 430, a portion of which can operate as aweb server for providing web portal services over the ISP network 432 towireline media devices 408 or wireless communication devices 416. Insome embodiments, the wireless communication device 116 can operate incombination with a 3GPP network such as the 3GPP mobile network 480.Alternatively or in addition, the wireless communication device 116 canoperate in combination with a non-3GPP network such as a WiFi accesspoint 482. The WiFi access point 482 can include access points managedby the mobile service provider of the 3GPP mobile network 480 and/orun-managed access points 482, such as public, domestic and/or enterpriseWiFi hotspots.

The communication system 400 can also provide for all or a portion ofthe computing devices 430 to function as a slice switching and/or3GPP/non-3GPP handover controller (herein referred to as reconfigurationcontroller 430). The reconfiguration controller 430 can use computingand communication technology to perform function 462, which can includeamong other things, the reconfiguration techniques described byprocesses 300, 350 of FIGS. 3A and 3B. For instance, function 462 of thereconfiguration controller 430 can be similar to the functions describedfor the UE 116, the service layer cloud, 125, the SDN controllers130-145, the management gateway 142, the administrative PDN 222, theePDG 220, the MME 214, the S-GW 216, the P-GW 218, the HSS 217, the AAA218, the eNodeB 206 and/or the WiFi access point 210 of FIGS. 1-2 inaccordance with process 300. The media processors 406 and wirelesscommunication devices 416 can be provisioned with software functions 464and 465, respectively, to utilize the services of the reconfigurationcontroller 430. For instance, function 464 and 466 of media processors406 and wireless communication devices 416 can be similar to thefunctions described for the communication devices 116, 202 of FIGS. 1-2in accordance with the processes 300, 350 of FIGS. 3A and 3B.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 417 operating according to common wireless access protocolssuch as Global System for Mobile or GSM, Code Division Multiple Accessor CDMA, Time Division Multiple Access or TDMA, Universal MobileTelecommunications or UMTS, World interoperability for Microwave orWiMAX, Software Defined Radio or SDR, Long Term Evolution or LTE, and soon. Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 5 depicts an illustrative embodiment of a communication system 500employing an IP Multimedia Subsystem (IMS) network architecture tofacilitate the combined services of circuit-switched and packet-switchedsystems. Communication system 500 can be overlaid or operably coupledwith systems 100, 200 of FIGS. 1 and/or 2 and communication system 400as another representative embodiment of communication system 400. Aservice is accessed by a first network operating within a first wirelessspectrum, wherein the service includes control and data forwardingoperations of the first network are separate and configured tofacilitate forwarding of user data via the data forwarding operations. Asecond network is identified operating within a second wirelessspectrum. A request that the accessing of the network service betransferred to the second network is made without interrupting theforwarding of the user data. A response to the request is detected viathe control operations, also without interrupting the forwarding of theuser data. Responsive to an indication that the second network has beenconfigured to accommodate a redirection of the forwarding of the userdata from the first network to the second, the redirection isfacilitated.

Communication system 500 can comprise a Home Subscriber Server (HSS)540, a tElephone NUmber Mapping (ENUM) server 530, and other networkelements of an IMS network 550. The IMS network 550 can establishcommunications between IMS-compliant communication devices (CDs) 501,502, Public Switched Telephone Network (PSTN) CDs 503, 505, andcombinations thereof by way of a Media Gateway Control Function (MGCF)520 coupled to a PSTN network 560. The MGCF 520 need not be used when acommunication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PSTN CD may utilize theMGCF 520.

IMS CDs 501, 502 can register with the IMS network 550 by contacting aProxy Call Session Control Function (P-CSCF) which communicates with aninterrogating CSCF (I-CSCF), which in turn, communicates with a ServingCSCF (S-CSCF) to register the CDs with the HSS 540. To initiate acommunication session between CDs, an originating IMS CD 501 can submita Session Initiation Protocol (SIP INVITE) message to an originatingP-CSCF 504 which communicates with a corresponding originating S-CSCF506. The originating S-CSCF 506 can submit the SIP INVITE message to oneor more application servers (ASs) 517 that can provide a variety ofservices to IMS subscribers.

For example, the application servers 517 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 506 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 506 can submit queries to the ENUMsystem 530 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 507 to submit a query to the HSS 540 toidentify a terminating S-CSCF 514 associated with a terminating IMS CDsuch as reference 502. Once identified, the I-CSCF 507 can submit theSIP INVITE message to the terminating S-CSCF 514. The terminating S-CSCF514 can then identify a terminating P-CSCF 516 associated with theterminating CD 502. The P-CSCF 516 may then signal the CD 502 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 5 may be interchangeable. It is further noted that communicationsystem 500 can be adapted to support video conferencing. In addition,communication system 500 can be adapted to provide the IMS CDs 501, 502with the multimedia and Internet services of communication system 400 ofFIG. 4.

If the terminating communication device is instead a PSTN CD such as CD503 or CD 505 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 530 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 506 to forward the call to the MGCF 520 via a Breakout GatewayControl Function (BGCF) 519. The MGCF 520 can then initiate the call tothe terminating PSTN CD over the PSTN network 560 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 5 can operate as wirelineor wireless devices. For example, the CDs of FIG. 5 can becommunicatively coupled to a cellular base station 521, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 550 of FIG. 5. The cellular accessbase station 521 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 5.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 521 may communicate directly with the IMS network 550 as shownby the arrow connecting the cellular base station 521 and the P-CSCF516.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

The reconfiguration controller 430 of FIG. 4 can be operably coupled tocommunication system 500 for purposes similar to those described above.The reconfiguration controller 430 can perform function 462 and therebyprovide slice and/or access network/point reconfiguration services tothe CDs 501, 502, 503 and 505 of FIG. 5 similar to the functionsdescribed for the UE 116, the service layer cloud, 125, the SDNcontrollers 130-145, the management gateway 142, the administrative PDN222, the ePDG 220, the MME 214, the S-GW 216, the P-GW 218, the HSS 217,the AAA 218, the eNodeB 206 and/or the WiFi access point 210 of FIGS.1-2 in accordance with process 300, 350 of FIGS. 3A and 3B. CDs 501,502, 503 and 505, which can be adapted with software to perform function572 to utilize the services of the reconfiguration controller 430similar to the functions described for communication devices 116, 202 ofFIGS. 1-2 in accordance with the processes 300, 350 of FIGS. 3A and 3B.The reconfiguration controller 430 can be an integral part of theapplication server(s) 517 performing function 574, which can besubstantially similar to function 462 and adapted to the operations ofthe IMS network 550.

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as 3^(rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 6 depicts an illustrative embodiment of a web portal 602 of acommunication system 600. Communication system 600 can be overlaid oroperably coupled with systems 100-200 of FIGS. 1 and/or 2, communicationsystem 400, and/or communication system 500 as another representativeembodiment of systems 100, 200 of FIGS. 1 and/or 2, communication system400, and/or communication system 500. The web portal 602 can be used formanaging services of systems 100, 200 of FIGS. 1 and/or 2 andcommunication systems 400-500. A web page of the web portal 602 can beaccessed by a Uniform Resource Locator (URL) with an Internet browserusing an Internet-capable communication device such as those describedin FIGS. 1 and/or 2 and FIGS. 4-5. The web portal 602 can be configured,for example, to access a media processor 406 and services managedthereby such as a Digital Video Recorder (DVR), a Video on Demand (VoD)catalog, an Electronic Programming Guide (EPG), or a personal catalog(such as personal videos, pictures, audio recordings, etc.) stored atthe media processor 406. The web portal 602 can also be used forprovisioning IMS services described earlier, provisioning Internetservices, provisioning cellular phone services, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 462-466, and 572-574 to adapt these applicationsas may be desired by subscribers and/or service providers of systems100, 200 of FIGS. 1 and/or 2, and communication systems 400-500. Forinstance, users of the services provided by the reconfigurationcontroller 430 can log into their on-line accounts and provision theservice layer 125, the SDN controller 130-145, the management gateway142, the servers 214, 217, 218, 220, 216, 218, 224, 430, the wirelessaccess points 116, 206, 210, 417, 482 and/or the devices 116, 202, 416with one or more of user profiles, SLAs, logic, preferences,subscriptions, authorization data, to provide contact information to anyone or more of the aforementioned devices to facilitate dynamic sliceswitching and/or 3GPP/non-3GPP handovers with devices described in FIGS.1-5, and so on. Service providers can log onto an administrator accountto provision, monitor and/or maintain the systems 100, 200 of FIGS. 1and/or 2 or server 430.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and/or 2, andFIGS. 4-5 and can be configured to perform at least portions of theprocesses 300, 350 of FIGS. 3A and 3B.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 702 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 700 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 700.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 700 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofdevices of FIGS. 1 and/or 2, the media processor 406, the media devices408, or the portable communication devices 416 of FIG. 4, as well as theIMS CDs 501-502 and PSTN CDs 503-505 of FIG. 5. It will be appreciatedthat the communication device 700 can also represent other devices thatcan operate in systems 100, 200 of FIGS. 1 and/or 2, communicationsystems 400-500 of FIGS. 4-5 such as a gaming console and a mediaplayer. In addition, the controller 706 can be adapted in variousembodiments to perform the functions 462-466 and 572-574, respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, one or more of the systems and/orprocesses disclosed herein can provide a multi slicing on demandcapability. One or more subscriber UE can submit an initial request forservice within a 3GPP 5G network. The request is intercepted by amanagement gateway that can receive multiple initial service requestfrom the selective subscriber UE. The management gateway forwards theinitial service request to a service layer cloud, which examines each ofsubscriber UE requirement. Requirements can include, without limitation,service type, QoS, and subscriber type, e.g., enterprise, single sub,etc. The service layer cloud sends the command to an SDN controller andthe management gateway, which evaluate the requests to determine orotherwise identify one or more logical network slice resources andavailability in association with each service request. The SDNcontroller and the management gateway assign particular slice to each ofthe service requests. The SDN controller and the management gatewayforward traffic, both control plane and user plane to a correct singlelogical network slice and/or multiple logical network slices for each ofthe service requests. In an event that none of the available singleslices is capable to support the initial request for service, multipleslice can be assigned to simultaneously support the requested service.

Alternatively or in addition, one or more of the systems and/orprocesses disclosed herein can provide a dynamic multi-slicingcapability, e.g., that can be invoked based on one or more of a profileand/or policy, e.g., according to a subscription level, such as apremium subscription. Alternatively or in addition, the capability canbe invoked based on one or more of an emergency adaption, networkcapacity, e.g., network load, geographic location of the UE, serviceavailability, and the like. It is further understood that the dynamicmulti-slicing capability can be terminated and/or re-established basedon profile and/or policy according to any of the foregoing parameters.In at least some embodiments, the dynamic multi-slicing capability canbe pre-scheduled based on profile and/or policy according to any of theforegoing parameters. Other embodiments can be used in the subjectdisclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the reconfiguration controller 430, the mediaprocessor 406, the UE 116, the service layer cloud, 125, the SDNcontrollers 130-145, the management gateway 142, the administrative PDN222, the ePDG 220, the MME 214, the S-GW 216, the P-GW 218, the HSS 217,the AAA 218, the eNodeB 206 and/or the WiFi access point 210 and otherdevices of FIGS. 1-2 and 4-5. In some embodiments, the machine may beconnected (e.g., using a network 826) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in a server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a display unit 810 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 800may include an input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker or remote control) and a network interfacedevice 820. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units810 controlled by two or more computer systems 800. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 810, while the remainingportion is presented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee®), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 800. In one or more embodiments, information regardinguse of services can be generated including services being accessed,media consumption history, user preferences, and so forth. Thisinformation can be obtained by various methods including user input,detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user. In one or more embodiments, ananalysis of data can be subject to authorization from user(s) associatedwith the data, such as an opt-in, an opt-out, acknowledgementrequirements, notifications, selective authorization based on types ofdata, and so forth.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A system, comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, the operations comprising: receiving a request to allow amobile device accessing a mobile service via a first wireless accesspoint operating within a first radio frequency spectrum, to access themobile service via a second wireless access point operating within asecond radio frequency spectrum, wherein control plane operations areseparate from data plane operations and configured to facilitate aforwarding of user data via the data plane operations, wherein the firstradio frequency spectrum comprises one of a managed frequency spectrumand an unmanaged frequency spectrum, and wherein the second radiofrequency spectrum comprise a different one of the managed frequencyspectrum and the unmanaged frequency spectrum; evaluating the request toallow the mobile device to access the mobile service via the secondwireless access point, to obtain an evaluation; and facilitating aredirection of the forwarding of the user data via the data planeoperations to the second wireless access point, responsive to therequest, the request being initiated via the control plane operations,without interrupting the forwarding of the user data via the data planeoperations of the first wireless access point.
 2. The system of claim 1,wherein the facilitating of the redirection of the forwarding of theuser data via the data plane operations to the second wireless accesspoint further comprises a reconfiguration of the mobile device.
 3. Thesystem of claim 2, wherein the reconfiguration of the mobile devicecomprises a reconfiguration of a radio, an antenna or both, processingwireless signals within the first radio frequency spectrum to processingwireless signals within the second radio frequency spectrum.
 4. Thesystem of claim 1, wherein the facilitating of the redirection of theforwarding of the user data via the data plane operations from the firstwireless access point to the second wireless access point furthercomprises redirecting control plane operations and user plane operationsto a different logical network slice.
 5. The system of claim 1, whereinthe first wireless access point operating within the first radiofrequency spectrum comprises a 3GPP mobile network.
 6. The system ofclaim 5, wherein the 3GPP mobile network comprises a 5G mobile networkcomprising a plurality of logical network slices configurable toaccommodate the control plane operations and the data plane operations.7. The system of claim 1, wherein the request initiated via the controlplane operations occurs responsive to an identifying of the secondwireless access point operating within the second radio frequencyspectrum.
 8. The system of claim 7, wherein the identifying of thesecond wireless access point operating within the second radio frequencyspectrum further comprises receiving a message via the control planeoperations of the first wireless access point identifying the secondwireless access point.
 9. A method, comprising: obtaining, by aprocessing system including processor, a request to allow a mobiledevice accessing a mobile service via a first portion of a wirelessnetwork operating within a first radio frequency spectrum, to access themobile service via a second portion of the wireless network operatingwithin a second radio frequency spectrum, wherein control operations areseparate from data forwarding operations and configured to facilitate aforwarding of user data via the data forwarding operations, wherein thefirst radio frequency spectrum comprises one of a managed frequencyspectrum and an unmanaged frequency spectrum, and wherein the secondradio frequency spectrum comprise a different one of the managedfrequency spectrum and the unmanaged frequency spectrum; evaluating, bythe processing system, the request to allow the mobile device to accessthe mobile service via the second portion of the wireless network, toobtain an evaluation; and initiating, by the processing system, aredirection of the forwarding of the user data via the data forwardingoperations to the second portion of the wireless network, responsive tothe request, the request being initiated via the control operations,without interrupting the forwarding of the user data via the dataforwarding operations of the wireless network.
 10. The method of claim9, wherein the facilitating of the redirection of the forwarding of theuser data via the data forwarding operations to the second portion ofthe wireless network further comprises a reconfiguration of a mobiledevice.
 11. The method of claim 10, wherein the reconfiguration of themobile device comprises a reconfiguration of a radio, an antenna orboth, processing wireless signals within the first radio frequencyspectrum to processing wireless signals within the second radiofrequency spectrum.
 12. The method of claim 9, wherein the first portionof the wireless network comprises a first logical network slice and thesecond portion of the wireless network comprises a second logical slice.13. The method of claim 9, wherein the first portion of the wirelessnetwork operating within the first radio frequency spectrum comprises a3GPP mobile network.
 14. The method of claim 13, wherein the 3GPP mobilenetwork comprises a 5G mobile network comprising a plurality of logicalnetwork slices configurable to accommodate the control operations andthe data forwarding operations.
 15. The method of claim 9, wherein therequest initiated via the control operations, occurs responsive to anidentifying of the second portion of the wireless network operatingwithin a second radio frequency spectrum.
 16. The method of claim 15,wherein the identifying of the second portion of the wireless networkoperating within a second radio frequency spectrum further comprisesreceiving, by the processing system, a message via the controloperations of the first portion of the wireless network identifying thesecond portion of the wireless network.
 17. A non-transitory,machine-readable storage medium, comprising executable instructionsthat, when executed by a processing system including a processor,facilitate performance of operations, the operations comprising:evaluating a request to allow a wireless device accessing a networkservice by a first portion of a network operating within a firstwireless spectral region to access the network service via a secondportion of the network operating within a second wireless spectralregion, wherein control operations are separate from data forwardingoperations and configured to facilitate a forwarding of user data viathe data forwarding operations, wherein the first wireless spectralregion comprises one of a managed spectral region and an unmanagedspectral region, and wherein the second wireless spectral regioncomprise a different one of the managed spectral region and theunmanaged spectral region; and facilitating a redirection of theforwarding of the user data to the second portion of the network,responsive to the request, without interrupting the forwarding of theuser data via the data forwarding operations.
 18. The non-transitory,machine-readable storage medium of claim 17, wherein the facilitating ofthe redirection of the forwarding of the user data via the dataforwarding operations to the second portion of the network furthercomprises a reconfiguration of a mobile device.
 19. The non-transitory,machine-readable storage medium of claim 18, wherein the reconfigurationof the mobile device comprises a reconfiguration of a radio, an antennaor both, processing wireless signals within the first wireless spectralregion to processing wireless signals within the second wirelessspectral region.
 20. The non-transitory, machine-readable storage mediumof claim 17, wherein the first portion of the network comprises a firstlogical network slice and the second portion of the network comprises asecond logical slice.